System and method for bandwidth utilization

ABSTRACT

Methods of bandwidth utilization are provided. Within a scheduling bandwidth, which may be an entire carrier bandwidth or a sub-band, scheduling is used to reserve a guard zone at the edge of the scheduled bandwidth. This can be based on the frequency localization capabilities of a transmitter that is to be scheduled. The guard zone may be defined to a resolution that is the same as the scheduling resolution in which case the guard zone is defined entirely through scheduling. Alternatively, the guard zone may be defined to a resolution smaller than the scheduling resolution in which case scheduling and further signaling may be employed to define the guard zone.

CROSS REFERENCE TO RELATED APPLICATION

This application claims priority to U.S. Provisional Application No.62/336,232 filed May 13, 2016, entitled “System and Method for BandwidthUtilization”, the contents of which are incorporated by reference hereinin their entirety.

FIELD

The application relates to systems and methods for bandwidthutilization.

BACKGROUND

In conventional networks, a carrier bandwidth is associated with aparticular carrier frequency. Within an overall system bandwidth, theremight be multiple carriers, each having a respective carrier bandwidth.Within each carrier bandwidth, respective guard bands are defined at thelow frequency end and at the high frequency end to achieve channelseparation between adjacent carriers.

SUMMARY

Methods of bandwidth utilization are provided. Within a schedulingbandwidth, which may be an entire carrier bandwidth or a sub-band,scheduling is used to implement a guard zone at the edge of thescheduled bandwidth. This can be based on the frequency localizationcapabilities of a transmitter that is to be scheduled. The guard zonemay be defined to a resolution that is the same as the schedulingresolution in which case the guard zone is defined entirely throughscheduling. Alternatively, the guard zone may be defined to a resolutionsmaller than the scheduling resolution in which case scheduling andfurther signaling may be employed to define the guard zone.Advantageously, more efficient bandwidth utilization may be achievedcompared to an implementation in which guard zones are permanentlyreserved adjacent to scheduling bandwidths.

According to one aspect of the present invention, there is provided amethod comprising: scheduling transmissions within a channelizationframework that occupies an entire carrier bandwidth; the schedulingcomprising scheduling no transmissions in at least one subcarrier at anedge portion of the carrier bandwidth.

Optionally, for any of the above described embodiments, the at least onesubcarrier at the edge portion is assigned based on a transmittedwaveform type.

Optionally, for any of the above described embodiments, the schedulingno traffic in at least one subcarrier at an edge portion of the carrierbandwidth is in response to a determination that a first guard zone isneeded.

Optionally, for any of the above described embodiments, schedulingtransmissions within a channelization framework that occupies an entirecarrier bandwidth comprises scheduling transmissions within a firstsub-band and a second sub-band adjacent to the first sub-band; themethod further comprising scheduling no transmissions in at least onesubcarrier in the first sub-band at an edge of the first sub-bandadjacent the second sub-band.

Optionally, for any of the above described embodiments, scheduling notransmissions in at least one subcarrier in the first sub-band at anedge of the first sub-band adjacent the second sub-band is in responseto a determination that a second guard zone is needed.

Optionally, for any of the above described embodiments, scheduling notransmissions in at least one subcarrier at an edge portion of thecarrier bandwidth is performed based on one or a combination of:transmitter frequency localization capability; receiver frequencylocalization capability; transmitter frequency localization capabilityand receiver frequency localization capability; transmit waveform type.

Optionally, for any of the above described embodiments, the methodfurther comprises receiving signaling indicating transmitter frequencylocalization capability.

Optionally, for any of the above described embodiments, scheduling notransmissions in at least one subcarrier at an edge portion of thecarrier bandwidth performed to a resolution that is one of: an integermultiple of a minimum scheduling resource unit; resource block group;fractional resource block group; resource block; fractional resourceblock; sub-carrier.

Optionally, for any of the above described embodiments, the methodfurther comprises transmitting further signaling to schedule notransmissions to a resolution that is smaller than a schedulingresolution, the signaling indicating that part of a scheduled resourceis for traffic and part is for guard zone.

Optionally, for any of the above described embodiments, the methodfurther comprises for each of a plurality of adjacent sub-bands withinthe carrier bandwidth, using a respective subcarrier spacing; whereinscheduling transmissions within a channelization framework that occupiesan entire carrier bandwidth further comprises scheduling notransmissions at the edges of adjacent sub-bands to create guard bandsbetween adjacent sub-bands.

Optionally, for any of the above described embodiments, the schedulingis for downlink transmissions, the method further comprisingtransmitting in accordance with the scheduling.

Optionally, for any of the above described embodiments, the schedulingis for uplink transmissions, the method further comprising: transmittingsignaling defining the scheduling.

Optionally, or any of the above described embodiments, scheduling fortraffic is performed to a resolution of resource block, and the guardzone is defined to a resolution finer than resource block, the methodfurther comprising transmitting signaling defining one of: fractional RButilization, subcarrier utilization.

Optionally, for any of the above described embodiments, scheduling fortraffic is performed to a resolution of resource block group, and theguard zone is defined to a resolution finer than resource block group,the method further comprising transmitting signaling defining one of:fractional RBG, RB, fractional RB utilization, subcarrier utilization.

Optionally, for any of the above described embodiments, schedulingwithin the entire carrier bandwidth is based on a set of full resourceblocks and at least one partial resource block.

Optionally, for any of the above described embodiments, the methodfurther comprises transmitting signaling to define the at least onepartial resource block.

Optionally, for any of the above described embodiments, scheduling overthe entire carrier bandwidth is performed over a first scheduledbandwidth based on a set of full resource blocks and at least onepartial resource block defined across the first scheduled bandwidth, andover a second scheduled bandwidth adjacent the first scheduled bandwidthbased on a set of full resource blocks and at least one partial resourceblock defined across the second scheduled bandwidth.

Optionally, for any of the above described embodiments, scheduling theentire carrier bandwidth is performed over a first scheduled bandwidthand a second scheduled bandwidth based on a set of full resource blocksand at least one partial resource block defined across adjacent edges ofthe first scheduled bandwidth and the second scheduled bandwidth.

According to another aspect of the present invention, there is provideda method in a user equipment, the method comprising: receiving ascheduling assignment within a channelization framework that occupies anentire carrier bandwidth, the scheduling assignment scheduling notransmissions in at least one subcarrier at an edge portion of thecarrier bandwidth; transmitting in accordance with the schedulingassignment.

Optionally, for any of the above described embodiments, the methodfurther comprises transmitting signaling indicating transmitterfrequency localization capability.

Optionally, for any of the above described embodiments, scheduling notransmissions in at least one subcarrier at an edge of the firstscheduled bandwidth for the guard zone is to a resolution that is oneof: an integer multiple of a minimum scheduling resource unit; resourceblock group; fractional resource block group; resource block; fractionalresource block; sub-carrier.

According to another aspect of the present invention, there is provideda base station comprising: a scheduler configured to scheduletransmissions within a first channelization framework that occupies a anentire carrier bandwidth; the scheduling comprising scheduling notransmissions in at least one subcarrier at an edge portion of thecarrier bandwidth; a transmitter for transmitting downlink transmissionsin accordance with the scheduling and/or a receiver for receiving uplinktransmissions in accordance with the scheduling.

Optionally, for any of the above described embodiments, the scheduler isfurther configured to: schedule transmissions within a channelizationframework that occupies the entire carrier bandwidth by schedulingtransmissions within a first scheduled bandwidth and a second scheduledbandwidth adjacent the first scheduled bandwidth; the method furthercomprising scheduling no transmissions in at least one subcarrier in thefirst sub-band at an edge of the first sub-band adjacent the secondsub-band.

Optionally, for any of the above described embodiments, scheduling notransmissions is performed to a resolution that is one of: an integermultiple of a minimum scheduling resource unit; resource block group;fractional resource block group; resource block; fractional resourceblock; sub-carrier.

According to another aspect of the present invention, there is provideda user equipment comprising: a receiver configured to receive ascheduling assignment within a first channelization framework thatoccupies an entire carrier bandwidth, the scheduling assignmentscheduling no transmissions in at least one subcarrier at an edgeportion of the carrier bandwidth; a transmitter configure to transmit inaccordance with the scheduling assignment.

Optionally, for any of the above described embodiments, the userequipment is further configured to transmit signaling indicatingtransmitter frequency localization capability.

Optionally, for any of the above described embodiments, scheduling notransmissions in at least one subcarrier at an edge portion of thecarrier bandwidth is performed to a resolution that is one of: aninteger multiple of a minimum scheduling resource unit; resource blockgroup; fractional resource block group; resource block; fractionalresource block; sub-carrier.

Optionally, for any of the above described embodiments, the receiver isfurther configured to receive further signaling when no traffic is to bescheduled to a resolution that is smaller than a scheduling resolution,the signaling indicating that part of a scheduled resource is fortraffic and part is for guard zone.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments of the disclosure will now be described with reference tothe attached drawings in which:

FIG. 1 is an example of conventional bandwidth utilization;

FIG. 2 is an example of bandwidth utilization in accordance with anembodiment of the invention;

FIG. 3A is an example of bandwidth utilization in accordance with anembodiment of the invention in which entire resource blocks are assignedthrough scheduling to function as guard zones;

FIG. 3B is an example of bandwidth utilization in accordance with anembodiment of the invention in which fractional resource blocks areassigned through scheduling to function as guard zones;

FIG. 3C is an example of bandwidth utilization in accordance with anembodiment of the invention in which scheduling is based on resourceblock groups, and guard zones are assigned to a resolution of resourceblock group, fractional resource block group, resource block, fractionalresource block or sub-carrier;

FIG. 3D is an example of bandwidth utilization where a carrier bandwidthis divided into sub-bands;

FIG. 3E is an example of continuous sub-carrier indexing within acarrier bandwidth across multiple sub-bands having a single sub-carrierspacing;

FIG. 3F is an example of sub-carrier indexing that re-starts in eachsub-band within a carrier bandwidth for multiple sub-bands having asingle sub-carrier spacing;

FIG. 3G is an example of continuous sub-carrier indexing within acarrier bandwidth across multiple sub-bands having different sub-carrierspacings;

FIG. 3H is an example of sub-carrier indexing that re-starts in eachsub-band within a carrier resource bandwidth for multiple sub-bandshaving a different sub-carrier spacings;

FIG. 3I shows a resource block definition scheme in which resourceblocks are defined across an entire carrier bandwidth;

FIG. 4A is a block diagram of a transmitter;

FIG. 4B is a block diagram of a receiver;

FIG. 5 is a flowchart of a method of bandwidth utilization provided byan embodiment of the invention;

FIG. 6 is a block diagram of a base station; and

FIG. 7 is a block diagram of a wireless device.

DETAILED DESCRIPTION

Generally, embodiments of the present disclosure provide a method andsystem for bandwidth utilization. For simplicity and clarity ofillustration, reference numerals may be repeated among the figures toindicate corresponding or analogous elements. Numerous details are setforth to provide an understanding of the examples described herein. Theexamples may be practiced without these details. In other instances,well-known methods, procedures, and components are not described indetail to avoid obscuring the examples described. The description is notto be considered as limited to the scope of the examples describedherein.

FIG. 1 is a logical diagram showing an example of partial bandutilization. Shown is a carrier bandwidth 100. Within that carrierbandwidth 100 is defined a channelization bandwidth 104 within which achannelization framework is defined, excluding guard bands 102 and 106.The channelization framework is defined such that resources can beallocated only within the channelization bandwidth 104.

In accordance with an embodiment of the invention, for a given carrier,a channelization framework is defined that occupies the entire carrierbandwidth. With this approach, the carrier bandwidth of an adjacentcarrier can be immediately adjacent to the carrier bandwidth of thesubject carrier. This approach can be applied for all carriers within amulti-carrier system, or only for a subset of the carriers. Filtering orwindowing can be performed to localize the spectrum of the transmittedwaveform. An example is depicted in FIG. 2. Shown is a carrier bandwidth200. Channelization is performed using a channelization framework thatoccupies a channelization bandwidth 202 that occupies the entire carrierbandwidth 200. A signaling scheme allows the allocation of channelsacross the entire channelization bandwidth. In this case, because thechannelization bandwidth 202 occupies the entire carrier bandwidth 200,the signaling scheme also allows the allocation of channels across theentire carrier bandwidth.

Depending on the nature of the signals to be transmitted using thechannelization framework thus defined, there may be a need for a guardzone on one or both ends of the carrier bandwidth. However, rather thanhaving fixed guard zones, as in the conventional approach of FIG. 1, inthese embodiments, the necessary guard zone or zones are achievedthrough scheduling. This approach can be applied to uplink transmissionsor downlink transmissions or both uplink and downlink transmissions.

In a first example, the carrier bandwidth is divided into a plurality ofresource blocks. Each resource block occupies a set of sub-carriers inthe frequency domain. On the uplink, scheduling is used to assignspecific user equipment (UEs) to transmit on specified resource blocksfor uplink transmission. The scheduling mechanism allows any of theresource blocks to be assigned. Depending on a given channel utilizationscenario, the scheduler may allocate certain resource blocks or parts ofcertain resource blocks to function as guard zones, for example by notscheduling any traffic in those resource blocks. This resource blockassignment can be done persistently or dynamically, and may involvesignaling to the UE that identifies what resource blocks to use.Similarly, on the downlink, scheduling is used to assign specific RBsfor use in transmitting to particular UEs. Again, this can be persistentor dynamic.

An example of a subchannelization framework is depicted in FIG. 3A.Shown is a carrier bandwidth 300 divided into twenty resource blocks302, 304, . . . , 340. The subchannelization framework occupies theentire subcarrier bandwidth. The scheduling mechanism allows for theassignment of any of the twenty resource blocks 302, 304, . . . , 340.Scheduling is used to define guard zones. In the illustrated example, tocreate guard zones in the frequencies of resource blocks 302, 340,scheduling is performed in a manner that does not assign the resourceblocks 302, 340.

In some embodiments, the guard zone is allocated through scheduling inunits of resource blocks. In this case, the guard zone on either endoccupies an integer number of resource blocks. This is the case for theexample of FIG. 3A. If a resource block is 12 subcarriers wide infrequency, then the minimum guard zone width is 12 subcarriers.

In another embodiment, the guard zone is allocated at a finerresolution, for example fractions of a resource blocks. For example, ifthe guard zone is allocated in units that are half a resource block insize, and a resource block is 12 subcarriers wide, then the minimumguard zone width is 6 subcarriers. Where part of a resource block isassigned to a guard band, if that resource block is also assigned fortraffic, both transmitter and receiver need to be aware to use only theremaining portion of the resource block for data. A mechanism for thisis described below. An example is depicted in FIG. 3B, where guard zonesare defined that occupy half of each of resource blocks 302 and 340. Inresource block 302, portion 360 functions as a guard zone, and portion362 is available to contain data. Similarly, in resource block 340,portion 366 functions as a guard zone, and portion 364 is available tocontain scheduled content.

In some embodiments, the guard zone is allocated down to the resolutionof individual subcarriers. Again, where part of a resource block isassigned to a guard band, if that resource block is also assigned fortraffic, both transmitter and receiver need to be aware to use only theremaining portion of the resource block for data.

In some embodiments, the channelization framework includes grouping theresource blocks into resource block groups (RBGs), with a resource blockgroup being a minimum unit of allocation. For example, referring now toFIG. 3C, the 20 resource blocks of FIG. 3A may be grouped into RBG 350,352, 354, 356, 358 each having 4 resource blocks. In this embodiment,guard zones on the edges of the carrier bandwidth may be defined to theresolution of RBG, partial RBG, RB, fractional RB, or subcarrier asdefined previously.

In some embodiments, each guard zone is allocated as an integer multipleof a minimum scheduling resource unit, whatever that may be. Resourceblocks and resource block groups are two specific examples.

Where a guard zone is allocated to a resolution that is the same as thescheduling resolution (be that RBG or RB), no separate signaling isnecessary, because scheduling can be used to implement the guard zone.When a guard zone is allocated to a resolution that is other than thescheduling resolution, signaling can be employed to indicate the partialutilization.

In some embodiments, the scheduling is done to define guard zones thatare a function of a transmitted waveform type. For example, in someembodiments, a transmitted waveform type is either filtered OFDM(f-OFDM) or windowed OFDM (W-OFDM). The guard zone requirement may bedifferent for these two waveform types. In a specific example, firstguard zones (either in RBG, fractional RBG, RB, fractional RB, orsubcarriers) are allocated on edges of a band used to transmit f-OFDM,and second guard zones (either in RBG, RB, fractional RB, orsubcarriers) are allocated on edges of a band used to transmit W-OFDM.

In some embodiments, the sizes of the guard zones are based ontransmitter frequency localization capabilities. A transmitter with abetter frequency localization capability will have better spectrumconfinement than a transmitter with a poorer frequency localizationcapability. A relatively smaller guard zone can be implemented for atransmitter with better frequency localization compared to a transmitterwith poorer frequency localization. Filtering and windowing are twoexamples of frequency localization features.

In some embodiments, a carrier can be divided into two or moresub-bands, or can be considered itself as a single sub-band. Eachsub-band may use a same or different numerology. As an example, a singlecarrier is used to transmit signals with multiple different sub-carrierspacings in respective sub-bands. In some such embodiments, no guardband is defined between the sub-bands. Rather, a channelizationframework is defined that includes the entire sub-bands. For example,one sub-band of a carrier may be used for 15 kHz sub-carrier spacing,and another sub-band of the same carrier may be used for 30 kHzsub-carrier spacing. Scheduling is used to define guard bands betweenthe sub-bands.

In some embodiments, a carrier bandwidth will have a specified maximumsupported channelization bandwidth. In a particular embodiment, this is400 MHz. As a result, the bandwidth of any one sub-band will be equal orless than the maximum. In other embodiments, at least for singlenumerology usage within a carrier bandwidth, there is a specifiedmaximum number of subcarriers supported in the carrier. In a particularembodiment, this maximum might be 3300 or 6600. For mixed numerologycases used in a carrier, at least the numerology with the lowestsubcarrier spacing will have its total number of subcarriers in thecarrier (bandwidth) equal or less than the specified maximum.

Table 1 is an example table to provide the maximum bandwidths for agiven sub-carrier spacing to support a specified maximum number ofsub-carriers in a carrier bandwidth; for example, 15 kHz sub-carrierspacing in a carrier or sub-band can support a maximum bandwidth of 50MHz or 100 MHz, depending on the maximum number of sub-carriers in acarrier bandwidth. The minimum FFT size to support transmission on agiven carrier needs to be greater than the number of sub-carrierssupported. As a result, to support the maximum number of sub-carriers ina carrier bandwidth, the minimum FFT size in the carrier will be greaterthan 3300 or 6600. Note for the table two options are shown for eachsub-carrier spacing and specified maximum number of subcarriers percarrier, and these are referred to as Option 1 and Option 2 in thetable. Option 1 and Option 2 are based on different guard band factors.Specifically, Option 1 is based on a negligible guard band, and Option 2is based on a 10% guard band like LTE; other options include differentguard bands from Options 1 and 2 or even no guard bands. The bandwidthbeyond 400 MHz is not listed, because for this example the maximumchannel bandwidth supported per carrier is 400 MHz, and ‘-’ in the tablemeans this combination is not supported. A similar table can begenerated for other maximum numbers of sub-carriers, and other guardbands.

TABLE 1 Maximum bandwidths for a given sub-carrier spacing to support aspecified maximum number of sub-carriers in a carrier bandwidth SCS(kHz) 15 30 60 120 Maximum # of b/w b/w b/w b/w b/w b/w b/w b/wsubcarriers (MHz) (MHz) (MHz) (MHz) (MHz) (MHz) (MHz) (MHz) per carrierOption 1 Option 2 Option 1 Option 2 Option 1 Option 2 Option 1 Option 23300 50 55 100 110 200 220 400 — 6600 100 110 200 220 400 — — —

In some embodiments, a carrier bandwidth employing a single numerologyoccupies a total of N sub-carriers. The N sub-carriers are equallyspaced and sequentially ordered (e.g., 0, 1, . . . , N−1) over thecarrier bandwidth. The carrier band can be divided into multiplesub-bands; depending on the bandwidth of a sub-band, the sub-bandoccupies an integer number of the sub-carriers from the N sub-carriersto form its channelization bandwidth, and different sub-bands can occupydifferent sub-carriers from the N sub-carriers. In some suchembodiments, a fixed or configurable number (e.g., 12) of sub-carriersin a sub-band form one resource block (RB); two or more, RBs in thesub-bands form one RB group (RBG), the size of which may be fixed orconfigurable. Either one RB or one RBG can be used as the schedulingresolution. The sub-carriers in a sub-band may not be integer divisibleby the size of the RB (e.g. 12 sub-carriers). In some embodiments, theleft-over or remaining sub-carriers in each sub-band are used to definea partial RB; a partial RB can also be defined if one single sub-banduses the entire carrier bandwidth. For example, if a sub-band occupies abandwidth of 15 MHz with a numerology with sub-carrier spacing of 15kHz, the sub-band will have 1000 sub-carriers to form 83 RBs (each with12 sub-carriers) with the 4 remaining sub-carriers as a partial RB.

In an embodiment, the sub-carriers in a sub-band are organized to formRBs in a way such that the remaining sub-carriers (sub-carriers leftover after defining as many full resource blocks as possible in thesub-band) are divided to two groups that are put at the two edges of thesub-band. This results in two partial RBs. This may be done, forexample, by designating out one or more sub-carriers from the left-sideedge of the sub-band as a first partial RB, to the right of the firstpartial RB forming as many full RBs as possible to the right-side edgeof the sub-band, and designating remaining sub-carriers at theright-side edge as a second partial RB. For example, the remainingsub-carriers in a sub-band can be divided to be equal or roughly equalinto two groups that are put at the two end edges of the sub-band. Inanother embodiment, the remaining sub-carriers in a sub-band are put ateither end edge of the sub-band. The RBs, including the full RBs andpartial RBs, can be configured by the resource scheduler. In otherembodiments, a RB is used as a minimum scheduling resolution, and theorientations of the remaining sub-carriers or partial RB can beconfigured by using additional (on top of RB based scheduling)signaling(s), such as high-layer signaling, broadcast signaling,multi-cast signaling, slowing signaling or semi-static signaling, etc.

In some embodiments, a carrier bandwidth employs a single numerology andincludes multiple sub-bands. The number of sub-carriers used in asub-band is determined by its bandwidth and the sub-carrier spacingvalue of the numerology; for example, a sub-band with 15 MHz bandwidthusing 15 kHz sub-carrier spacing will have 1000 sub-carriers.

A sub-band can have its own sub-carrier orientation in terms ofindividual sub-carrier physical frequency location and index ordering ofthe sub-carriers. In some such embodiments, individual sub-carrierfrequency locations are associated with the sub-carrier orientations ofneighbor sub-bands; for example, all the sub-carrier frequency locationsamong different sub-bands align with a same (and global) sub-carriergrid across the carrier bandwidth, and the indexing on sub-carriers isglobally done within the carrier bandwidth. An example of this is shownin FIG. 3E where the sub-carriers for K sub-bands are indexedcontinuously from 0 to N−1, where N is the total number of sub-carriersfor the entire carrier. In another embodiment, the sub-carriers arere-numbered for each individual sub-band as shown in FIG. 3F. Theapproach with individually indexed sub-carriers in a sub-band can beemployed to data transmission for a UE not capable of supporting thecarrier bandwidth, together with a scheduling scheme that includes atwo-step information to configure or allocate sub-carriers for the datatransmissions. For example, resource allocation can be derived based ona two-step frequency-domain assignment process: 1st step: indication ofa bandwidth part, e.g., indication of one or more sub-bands; 2nd step:indication of the RBs within the bandwidth part. As in the exampledescribed above, the RBs do not necessarily need to be uniform in size.Partial RBs may be preconfigured by signaling.

In general, absent frequency localization features, such as f-OFDM orW-OFDM, a guard band is required between any two adjacent sub-bands, andbetween two neighboring carrier bands. For a given UE, the UE may or maynot support frequency localization features.

In some embodiments, a UE is configured to communicate its frequencylocalization capability to the network, for example to a transmissionand reception point (TRP). This might, for example, occur during initialsystem access. This enables the network to determine the UE capability,and based in part on that, to determine if a guard band is required ornot, and the size of the guard band if required.

In some embodiments, for a UE with an f-OFDM capability that isconfigured to transmit in a band using the f-OFDM capability, no guardband is required at all between the band and an adjacent band becausethe spectrum of the transmitted f-OFDM signal is well confined.

In some embodiments, for a UE with W-OFDM capability that is configuredto transmit in a band using the W-OFDM capability, some guard band isrequired between the band and an adjacent band, because the W-OFDMsignal is less well confined than an f-OFDM signal, so that thetransmitted W-OFDM signal does not interfere with transmissions in anadjacent band.

For a UE that either has neither capability (or more generally has nofrequency localization functionality), and for a UE that has somefrequency localization capability but is not configured to use it, aguard band will be required, typically larger than that required forW-OFDM.

In some embodiments, the size of a guard band can be indicated in ascheduling message. In some embodiments, multiple sub-bands occupy acarrier bandwidth with mixed numerologies. An example is depicted inFIG. 3D. Shown is a 60 MHz carrier bandwidth 380 divided into a 15 MHzfirst sub-band 382 using 15 kHz sub-carrier spacing, a 30 MHz secondsub-band 384 using a 30 kHz sub-carrier spacing, and a 15 MHz thirdsub-band 386 using a 15 kHz sub-carrier spacing. There is no pre-definedguard band defined between sub-bands 382 and 384, and no pre-definedguard band defined between sub-bands 384 and 386. Rather, any necessarychannel separation is achieved through scheduling, for example asdescribed above.

In other embodiments, multiple sub-bands occupy a carrier bandwidth withmixed numerologies; a sub-band with a numerology will have a number ofsub-carriers that are determined by its sub-band bandwidth and thesub-carrier spacing value of the numerology, for example, a sub-bandwith 30 MHz bandwidth using 30 kHz sub-carrier spacing will have 1000sub-carriers. A sub-band may have a different numerology from itsneighbor sub-band(s), and thus can have its own sub-carrier orientation,or individual sub-carrier physical location and index ordering. In somesuch embodiments, sub-carrier locations using the lowest sub-carrierspacing in the multiple sub-bands are used as a reference sub-carriergrid to align the sub-carriers and the sub-carrier indexing among allsub-bands in a carrier bandwidth with multiple scalable numerologies,where a sub-carriers in a larger sub-carrier spacing numerology takepositions in the reference grid to make the sub-carrier orientations forall sub-bands more convenient and thus system signaling configurationmore effective. An example is shown in FIG. 3G where the sub-carriers intwo sub-bands have different spacings, but all are located on the gridwith the smaller sub-carrier spacing. Sub-carrier indexing is continuousacross the entire carrier bandwidth.

In other embodiments, multiple sub-bands occupy a carrier bandwidth withmixed numerologies, where the sub-carrier indexing in a differentsub-band is renumbered or numbered relative to its associated sub-band.An example is shown in FIG. 3H which shows the same sub-carriers as theFIG. 3G example, but in which sub-carrier indexing is separate for eachsub-band. This approach may be suitable for data transmission for a UEnot capable of supporting the carrier bandwidth. In some embodiments,the two-step scheduling approach described above can be employed.

In some embodiments, multiple sub-bands occupy a carrier bandwidth witha minimum scheduling resolution of one RB, for a given RB size (e.g.,12). The RBs are formed sequentially from the sub-carriers over allsub-bands in a carrier bandwidth, leaving the remaining sub-carriers inonly one partial RB. An example is shown in FIG. 3I where thesub-carriers of a set of sub-bands are used to form L RBs, and onepartial RB. Note that the sub-bands occupying the carrier bandwidth caneither all have the same numerology or have mixed numerologies. In thisembodiment, the RB resources can be used most efficiently in theresource allocation scheduling, because only one partial RB remainsafter assigning the entire carrier bandwidth.

Depending on how many sub-bands there are, and depending also on thebandwidth division, in some embodiments, one RB may cross over an edgeof one sub-band into a neighbouring sub-band. Such an RB includesrespective parts that belong to each of the neighbouring sub-bands. FIG.3I contains two examples of this. In the first example, generallyindicated at 390, RB formulation occurs sequentially across the entirecarrier bandwidth with one partial RB left on the right side. In thesecond example, generally indicated at 392, there is a partial RB splitinto between two ends of the carrier bandwidth that includessub-carriers f₀ and f_(N-1). Alternatively, for the second example, twopartial RBs can be defined, one at each end. In both examples 390, 392,RB_(i) is an RB that crosses the boundary between neighbouringsub-bands. In some embodiments, additional signaling is used to indicatethe sub-band in which the RB is being scheduled. Alternatively, a twotwo-step frequency-domain assignment process can be employed, asdescribed above. This RB organization scheme is able to provide anefficient resource utilization for a UE with an f-OFDM capability thatis configured to transmit within a sub-band using the f-OFDM capability.No guard band is required between the sub-band and an adjacent sub-bandbecause the spectrum of the transmitted f-OFDM signal is well confined.In such an embodiment, guard bands may still be defined at the edge ofthe carrier bandwidth through scheduling, as described previously.

Embodiments described herein provide for the definition of guard bandsthrough scheduling at various resolutions, including individualsub-carriers and individual resource blocks. In some embodiments, wherethe guard band is defined to a resolution of one sub-carrier, thisscheduling can be based on one of the sub-carrier indexing schemesdescribed above. Where the guard band is defined to the resolution ofone resource block or a partial resource block, this scheduling can bebased on one of the resource block schemes described above. Optionally,this is combined with signaling to configure the sub-carrier indexingscheme and/or resource block definitions.

Referring now to FIG. 4A, shown is an example simplified block diagramof part of a transmitter that can be used to perform scheduling asdescribed above. In this example, there are L supported numerologies,where L>=2, each numerology operating over a respective sub-band with arespective sub-carrier spacing. However, this approach can be appliedwhen there is only a single numerology.

For each numerology, there is a respective transmit chain 400,402. FIG.4A shows simplified functionality for the first and Lth numerology; thefunctionality for other numerologies would be similar. Also shown inFIG. 4B is simplified functionality for a receive chain 403 for areceiver operating using the first numerology.

The transmit chain 400 for the first numerology includes a constellationmapper 410, subcarrier mapping and grouping block 411, IFFT 412 withsubcarrier spacing SC₁, pilot symbol and cyclic prefix insertion 414,and frequency localization operator 416 (for example filtering, sub-bandfiltering, windowing, sub-band windowing). Also shown is a scheduler 450that performs scheduling using one of the methods described herein, forexample the method of FIG. 5 described below, based on a channelizationthat occupies the entire sub-band bandwidths, with scheduling used toimplement any required guard zones. It is noted that depending on thefrequency localization operator implementation, different guard zonesmay be needed at the two edges of the spectrum and/or between sub-bandswith different numerologies (i.e. different sub-carrier spacings). Insome embodiments, the guard zones are determined taking into accountfrequency localization capabilities of both the transmitter andreceiver.

In operation, constellation mapper 410 receives UE data (more generally,UE content containing data and/or signalling) for K₁ UEs, where K₁>=1.The constellation mapper 410 maps the UE data for each of the K₁ UEs toa respective stream of constellation symbols and outputs this at 420.The number of UE bits per symbol depends on the particular constellationemployed by the constellation mapper 410. In the example of quadratureamplitude modulation (QAM), 2 bits from for each UE are mapped to arespective QAM symbol.

For each OFDM symbol period, the subcarrier mapping and grouping block411 groups and maps the constellation symbols produced by theconstellation mapper 410 to up to P inputs of the IFFT 412 at 422. Thegrouping and mapping is performed based on scheduler information, whichin turn is based on channelization and resource block assignment, inaccordance with a defined resource block definition and allocation forthe content of the K₁ UEs being processed in transmit chain 400. P isthe size of the IFFT 412. Not all of the P inputs are necessarily usedfor each OFDM symbol period. The IFFT 412 receives up to P symbols, andoutputs P time domain samples at 424. Following this, in someimplementations, time domain pilot symbols are inserted and a cyclicprefix is added in block 414. The frequency localization operator 416may, for example, apply a filter f₁(n) which limits the spectrum at theoutput of the transmit chain 400 to prevent interference with theoutputs of other transmit chains such as transmit chain 402. Thefrequency localization operator 416 also performs shifting of eachsub-band to its assigned frequency location.

The functionality of the other transmit chains, such as transmit chain402 is similar. The outputs of all of the transmit chains are combinedin a combiner 404 before transmission on the channel.

FIG. 4B shows a simplified block diagram of a receive chain for a userequipment operating with the first numerology depicted at 403. In someembodiments, a given user equipment is permanently configured to operatewith a particular numerology. In some embodiments, a given userequipment operates with a configurable numerology. In either case,flexible resource block definitions are supported by the user equipment.The receive chain 403 includes frequency localization operator 430,cyclic prefix deletion and pilot symbol processing 432, fast Fouriertransform (FFT) 434, subcarrier de-mapping 436 and equalizer 438. Eachelement in the receive chain performs corresponding reverse operationsto those performed in the transmit chain. The receive chain for a userequipment operating with another numerology would be similar.

The subcarrier mapping and grouping block 411 of FIG. 4A groups and mapsthe constellation symbols based on the resource block definition(s) andscheduling. The scheduler 450 of FIG. 4A decides where in time andfrequency the UE's resource blocks will be transmitted.

FIG. 5 is a flowchart of a method provided by an embodiment of theinvention. Optionally, the method begins in block 520 with the step ofreceiving signaling indicating transmitter frequency localizationcapability. In block 522, transmissions are scheduled within achannelization framework that occupies an entire carrier bandwidth. Inblock 524, through the scheduling, some capacity is reserved at an edgeof the carrier bandwidth to create a guard zone. Optionally, in block526, signalling is transmitted that defines the scheduling. This canindicate to a UE where downlink transmissions will occur, or canindicate to a UE where to make uplink transmissions. Optionally, inblock 528, downlink transmissions are made in accordance with thescheduling. The same approach can be employed to define a guard bandbetween adjacent sub-bands of a carrier, as detailed above. In thiscase, there is a respective channelization framework for each sub-bandthat occupies the entire sub-band, and scheduling is used to reservecapacity at an edge of a sub-band to create a guard zone betweenadjacent sub-bands.

Throughout this description, there are references to reserving capacityat an edge of a carrier bandwidth to create a guardband. More generally,no transmissions are scheduled in at least one sub-carrier at an edge ofa carrier bandwidth. This may be done in response to a determinationthat a guard zone is needed.

Thus, in an overall approach, there can be a carrier bandwidth that isdivided into multiple adjacent sub-bands. A respective channelizationframework is defined within each sub-band. Two of the sub-bands willshare an edge with the carrier bandwidth. Scheduling is used to defineguard zones at the edge of the carrier bandwidth. In addition oralternatively, scheduling is used to define guard zones at the edges ofadjacent sub-bands. For a given pair of adjacent sub-bands, there is apair of adjacent sub-band edges. Depending on a given situation, theguard zone between adjacent sub-bands can include a guard zone at one orthe other of the two sub-band edges, or at both sub-band edges.

FIG. 6 is a schematic block diagram of a BS 12 according to someembodiments of the present disclosure. As illustrated, the BS 12includes a control system 34 configured to perform the network sidefunctions described herein. In some implementations, the control system34 is in the form of circuitry configured to perform the network sidefunctions. In yet other implementations, the control system or circuitry34 includes one or more processors 36 (e.g., CPUs, ASICs, FPGAs, and/orthe like) and memory 38 and possibly a network interface 40. The BS 12also includes one or more radio units 42 that each includes one or moretransmitters 44 and one or more receivers 46 coupled to one or moreantennas 48. In some other implementations, the functionality of the BS12 described herein may be fully or partially implemented in software ormodules that is, e.g., stored in the memory 38 and executed by theprocessor(s) 36.

In yet other implementations, a computer program including instructionswhich, when executed by at least one processor, causes the at least oneprocessor to carry out the functionality of the BS 12 according to anyof the embodiments described herein is provided. In yet otherimplementations, a carrier containing the aforementioned computerprogram product is provided. The carrier is one of an electronic signal,an optical signal, a radio signal, or a computer readable storage medium(e.g., a non-transitory computer readable medium such as memory).

FIG. 7 is a schematic block diagram of the wireless device 14 accordingto some embodiments of the present disclosure. As illustrated, thewireless device 14 includes circuitry 18 configured to perform thewireless device functions described herein. In some implementations, thecircuitry 18 includes one or more processors 20 (e.g., CentralProcessing Units (CPUs), Application Specific Integrated Circuits(ASICs), Field Programmable Gate Arrays (FPGAs), and/or the like) andmemory 22. The wireless device 14 also includes one or more transceivers24 each including one or more transmitter 26 and one or more receivers28 coupled to one or more antennas 30. In some other implementations,the functionality of the wireless device 14 described herein may befully or partially implemented in software or modules that is, e.g.,stored in the memory 22 and executed by the processor(s) 20.

In yet other implementations, a computer program including instructionswhich, when executed by at least one processor, causes the at least oneprocessor to carry out the functionality of the wireless device 14according to any of the embodiments described herein is provided. In yetother implementations, a carrier containing the aforementioned computerprogram product is provided. The carrier is one of an electronic signal,an optical signal, a radio signal, or a computer readable storage medium(e.g., a non-transitory computer readable medium such as memory).

In the preceding description, for purposes of explanation, numerousdetails are set forth in order to provide a thorough understanding ofthe embodiments. However, it will be apparent to one skilled in the artthat these specific details are not required. In other instances,well-known electrical structures and circuits are shown in block diagramform in order not to obscure the understanding. For example, specificdetails are not provided as to whether the embodiments described hereinare implemented as a software routine, hardware circuit, firmware, or acombination thereof.

The above-described embodiments are intended to be examples only.Alterations, modifications and variations can be effected to theparticular embodiments by those of skill in the art. The scope of theclaims should not be limited by the particular embodiments set forthherein, but should be construed in a manner consistent with thespecification as a whole.

1. A method comprising: scheduling transmissions within a channelizationframework that occupies an entire carrier bandwidth; the schedulingcomprising scheduling no transmissions in at least one subcarrier at anedge portion of the carrier bandwidth.
 2. The method of claim 1 whereinthe at least one subcarrier at the edge portion is assigned based on atransmitted waveform type.
 3. The method of claim 1 wherein thescheduling no traffic in at least one subcarrier at an edge portion ofthe carrier bandwidth is in response to a determination that a firstguard zone is needed.
 4. The method of claim 3 wherein: schedulingtransmissions within a channelization framework that occupies an entirecarrier bandwidth comprises scheduling transmissions within a firstsub-band and a second sub-band adjacent to the first sub-band; themethod further comprising scheduling no transmissions in at least onesubcarrier in the first sub-band at an edge of the first sub-bandadjacent the second sub-band.
 5. The method of claim 4 whereinscheduling no transmissions in at least one subcarrier in the firstsub-band at an edge of the first sub-band adjacent the second sub-bandis in response to a determination that a second guard zone is needed. 6.The method of claim 1 wherein scheduling no transmissions in at leastone subcarrier at an edge portion of the carrier bandwidth is performedbased on one or a combination of: transmitter frequency localizationcapability; receiver frequency localization capability; transmitterfrequency localization capability and receiver frequency localizationcapability; transmit waveform type.
 7. The method of claim 1 furthercomprising: receiving signaling indicating transmitter frequencylocalization capability.
 8. The method of claim 1 wherein scheduling notransmissions in at least one subcarrier at an edge portion of thecarrier bandwidth performed to a resolution that is one of: an integermultiple of a minimum scheduling resource unit; resource block group;fractional resource block group; resource block; fractional resourceblock; sub-carrier.
 9. The method of claim 8 further comprising:transmitting further signaling to schedule no transmissions to aresolution that is smaller than a scheduling resolution, the signalingindicating that part of a scheduled resource is for traffic and part isfor guard zone.
 10. The method of claim 1 further comprising: for eachof a plurality of adjacent sub-bands within the carrier bandwidth, usinga respective subcarrier spacing; wherein scheduling transmissions withina channelization framework that occupies an entire carrier bandwidthfurther comprises scheduling no transmissions at the edges of adjacentsub-bands to create guard bands between adjacent sub-bands.
 11. Themethod of claim 1 wherein the scheduling is for downlink transmissions,the method further comprising transmitting in accordance with thescheduling.
 12. The method of claim 1 wherein the scheduling is foruplink transmissions, the method further comprising: transmittingsignaling defining the scheduling.
 13. The method of claim 3 whereinscheduling for traffic is performed to a resolution of resource block,and the guard zone is defined to a resolution finer than resource block,the method further comprising transmitting signaling defining one of:fractional RB utilization, subcarrier utilization.
 14. The method ofclaim 3 wherein scheduling for traffic is performed to a resolution ofresource block group, and the guard zone is defined to a resolutionfiner than resource block group, the method further comprisingtransmitting signaling defining one of: fractional RBG, RB, fractionalRB utilization, subcarrier utilization.
 15. The method of claim 1wherein scheduling within the entire carrier bandwidth is based on a setof full resource blocks and at least one partial resource block.
 16. Themethod of claim 17 further comprising transmitting signaling to definethe at least one partial resource block.
 18. The method of claim 1wherein scheduling over the entire carrier bandwidth is performed over afirst scheduled bandwidth based on a set of full resource blocks and atleast one partial resource block defined across the first scheduledbandwidth, and over a second scheduled bandwidth adjacent the firstscheduled bandwidth based on a set of full resource blocks and at leastone partial resource block defined across the second scheduledbandwidth.
 19. The method of claim 1 wherein scheduling the entirecarrier bandwidth is performed over a first scheduled bandwidth and asecond scheduled bandwidth based on a set of full resource blocks and atleast one partial resource block defined across adjacent edges of thefirst scheduled bandwidth and the second scheduled bandwidth.
 20. Amethod in a user equipment, the method comprising: receiving ascheduling assignment within a channelization framework that occupies anentire carrier bandwidth, the scheduling assignment scheduling notransmissions in at least one subcarrier at an edge portion of thecarrier bandwidth; transmitting in accordance with the schedulingassignment.
 23. The method of claim 20 further comprising: transmittingsignaling indicating transmitter frequency localization capability. 24.The method of claim 20 wherein scheduling no transmissions in at leastone subcarrier at an edge of the first scheduled bandwidth for the guardzone is to a resolution that is one of: an integer multiple of a minimumscheduling resource unit; resource block group; fractional resourceblock group; resource block; fractional resource block; sub-carrier. 25.A base station comprising: a scheduler configured to scheduletransmissions within a first channelization framework that occupies a anentire carrier bandwidth; the scheduling comprising scheduling notransmissions in at least one subcarrier at an edge portion of thecarrier bandwidth; a transmitter for transmitting downlink transmissionsin accordance with the scheduling and/or a receiver for receiving uplinktransmissions in accordance with the scheduling.
 26. The base station ofclaim 25 wherein the scheduler is further configured to: scheduletransmissions within a channelization framework that occupies the entirecarrier bandwidth by scheduling transmissions within a first scheduledbandwidth and a second scheduled bandwidth adjacent the first scheduledbandwidth; the method further comprising scheduling no transmissions inat least one subcarrier in the first sub-band at an edge of the firstsub-band adjacent the second sub-band.
 27. The base station of claim 25scheduling no transmissions is performed to a resolution that is one of:an integer multiple of a minimum scheduling resource unit; resourceblock group; fractional resource block group; resource block; fractionalresource block; sub-carrier.
 28. A user equipment comprising: a receiverconfigured to receive a scheduling assignment within a firstchannelization framework that occupies an entire carrier bandwidth, thescheduling assignment scheduling no transmissions in at least onesubcarrier at an edge portion of the carrier bandwidth; a transmitterconfigure to transmit in accordance with the scheduling assignment. 29.The user equipment of claim 28 further configured to transmit signalingindicating transmitter frequency localization capability.
 30. The userequipment of claim 28 wherein scheduling no transmissions in at leastone subcarrier at an edge portion of the carrier bandwidth is performedto a resolution that is one of: an integer multiple of a minimumscheduling resource unit; resource block group; fractional resourceblock group; resource block; fractional resource block; sub-carrier. 31.The user equipment of claim 28 wherein the receiver is furtherconfigured to receive further signaling when no traffic is to bescheduled to a resolution that is smaller than a scheduling resolution,the signaling indicating that part of a scheduled resource is fortraffic and part is for guard zone.